Pin GitHub Actions to specific commit SHAs for security#23
Merged
Conversation
Pin actions/checkout, actions/setup-node, and the remaining pnpm/action-setup uses to full commit SHAs to mitigate supply chain risk from compromised tags.
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR pins all GitHub Actions dependencies to specific commit SHAs instead of using version tags, improving supply chain security by preventing potential tag spoofing attacks.
Key Changes
v6tode0fac2e4500dabe0009e67214ff5f5447ce83dd(v6.0.2)v6to48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e(v6.4.0)v6.0.3tag references to903f9c1a6ebcba6cf41d87230be49611ac97822e(v6.0.3)Implementation Details
All GitHub Actions across three workflow files (ci.yml and release.yml) have been updated to use immutable commit SHAs with inline version comments for maintainability. This follows GitHub's security best practices by preventing potential attacks where a tag could be reassigned to a different commit.
https://claude.ai/code/session_017kCbKzZZ2VMzbxwYkAwgsf